Expected Differences

• Do these changes introduce new tools, command line arguments, or configuration file options? [No]
  
  If yes, please describe:
  

Pull Request Testing

• Describe testing already performed for these changes:
  

Reviewed in Google doc with team and reviewed in Read the Docs here.

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  

Review formatting in Read the Docs here and review values if desired.

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes]

• Do these changes include sufficient testing updates? [Yes]

• Will this PR result in changes to the test suite? [No]
  
  If yes, describe the new output and/or changes to the existing output:
  

• Please complete this pull request review by [Before the release].
  

Pull Request Checklist

• Complete the PR definition above.
• Ensure the PR title matches the feature or bugfix branch name.
• Select: Reviewer(s)
• After submitting the PR, select the ⚙️ icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
• After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• Close the linked issue and delete your feature or bugfix branch from GitHub.